Method, system, and computer-readable medium for simulating a converged network with a single media gateway and media gateway controller

ABSTRACT

A method, system, and computer-readable medium for emulating a converged network are provided. A media gateway receives a call at a first interface of a first network type. The call is processed for distribution on a second network type. The processed call is transmitted to a second interface of a second network type. A service module of the media gateway receives the processed call.

BACKGROUND

As wireless and wireline networks converge and network configurationsbecome increasingly complicated, realistic testing of end-to-end callsbecomes more complicated and expensive. Networks may comprise any numberof network entities that may, and typically are, manufactured by a widevariety of component manufacturers. Due to, among other reasons, thenumber of network components and network component costs, deployment ofsuitable network components in a test environment for evaluating one ormore network entities or functions becomes prohibitively expensive andimpractical.

Call testing in modern telecommunication systems is particularlyproblematic due to the fact that network systems may comprise componentsthat are manufactured by multiple vendors. Depending on the routingcomplexity of a test call, deployment of a realistic test environmentmay be unfeasible. It is often prohibitively costly to acquire therequisite network components to realistically evaluate a particularnetwork component or function.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are best understood from the followingdetailed description when read with the accompanying figures, in which:

FIG. 1 is a diagrammatic representation of an embodiment of an exemplarynetwork comprising wireless, wireline, and packet networks;

FIG. 2 is a diagrammatic representation of at least a portion of anetwork in which a test call may be evaluated in a conventional manner;

FIG. 3 is a diagrammatic representation of an embodiment of aconfiguration of interconnections between a media gateway, a mediagateway controller, and a network emulator;

FIG. 4A is a diagrammatic representation of an embodiment of a mediagateway that may be configured to emulate a converged network for mediagateway and call testing;

FIG. 4B is a diagrammatic representation of an embodiment of a logicalconfiguration of a media gateway for emulating a converged network;

FIG. 4C is a diagrammatic representation of an embodiment of a mediagateway depicted in FIG. 4B shown in a physical configuration foremulating a test call;

FIG. 4D is a diagrammatic representation of a converged networksimulated by the configuration of the media gateway shown in FIGS. 4Band 4C;

FIG. 5 is a diagrammatic representation of a configuration of a mediagateway controller depicted in FIG. 3 that facilitates converged networkemulation in accordance with embodiments disclosed herein;

FIG. 6 is a diagrammatic representation of an exemplary call signalingflow among a media gateway and various media gateway controllercomponents or functions that facilitates call set-up;

FIG. 7 is diagrammatic representation of a configuration of a networkemulator that drives network emulation and testing in accordance withembodiments disclosed herein;

FIG. 8 is a flowchart depicting a high level flow of an embodiment foremulating a converged network in accordance with embodiments disclosedherein;

FIG. 9 is a flowchart depicting call processing and call execution of atest call in an emulated converged network in accordance withembodiments disclosed herein; and

FIG. 10 is a flowchart depicting an embodiment of media gatewaycontroller processing for detection of a test call and processingthereof.

DETAILED DESCRIPTION

It is to be understood that the following disclosure provides manydifferent embodiments, or examples, for implementing different featuresof various embodiments. Specific examples of components and arrangementsare described below to simplify the present disclosure. These are, ofcourse, merely examples and are not intended to be limiting. Inaddition, the present disclosure may repeat reference numerals and/orletters in the various examples. This repetition is for the purpose ofsimplicity and clarity and does not in itself dictate a relationshipbetween the various embodiments and/or configurations discussed.

FIG. 1 is a diagrammatic representation of an embodiment of an exemplarynetwork 100 comprising wireless, wireline, e.g., PSTN, and packetnetworks. Network 100 may include several networks and/or portions ofnetworks. In the illustrative example, network 100 includes apparatus100 a-100 e. Apparatus 100 a is connected by a plurality of loops 115 toone or more PSTN access networks 110 that may include a plurality ofresidential telephones and/or business exchanges (PBXs). In oneembodiment, the telephones may be grouped by digital loop carriers,PBXs, and/or other aggregators which may be included in one or more ofthe PSTN access networks 110, or may otherwise be configured tocommunicate with the apparatus 100 a through PSTN access network 110.Loops 115 may include digital loops and/or analog loops, and may beconfigured to transmit TDM and other PSTN data, among others. Thus,apparatus 100 a may be implemented as a Class 5 central office switch.Accordingly, any PSTN access network 110 connected to apparatus 100 amay communicate with another PSTN access network 110 connected toapparatus 100 a.

Apparatus 100 a is also connected to apparatus 100 b by a trunk or othertransmission line 120. Apparatus 100 b is, in turn, connected to aplurality of residential telephones, business PBXs, digital loopcarriers, and/or PSTN access networks 112 (hereafter collectivelyreferred to as PSTN access networks 112, although merely for the sake ofsimplicity) by a corresponding plurality of loops 117, which may each besubstantially similar to one or more of loops 115. Thus, any of the PSTNaccess networks 110 may communicate with any of the PSTN access networks112 via apparatus 100 a and 100 b, trunk 120, and corresponding ones ofloops 115 and 117.

Apparatus 100 c may aggregate traffic from any number oftelecommunication nodes, such as apparatus 100 a, 100 b and 100 d, andthus may be implemented as a Class 4 switch. Apparatus 100 d may beimplemented as a switching media gateway (MGW) for providing variousswitching services and media handling across various platforms.Accordingly, apparatus 100 d may interface with one or more networks,such as PSTN 150 and packet network 160. Apparatus 100 d may provideboth Class 4 and Class 5 switching services and thus may aggregatetraffic from other network entities, such as apparatus 100 a and 100 c,and may provide switching services to termination points in networks 150and 160.

Additionally, network 100 may include a media gateway (MGW) 100 e tointerconnect a radio access network (RAN) 145 to one or more of accessnetworks 110 and 112, PSTN 150, and packet network 160. RAN 145 mayinclude a network controller (not shown) that is coupled with one ormore base transceiver stations 125 that provide an over-the-airinterface with one or more wireless mobile terminals 135. Conventionalcommunications may traverse any one or more of wireless, wireline, andpacket networks, and it is not uncommon for a call to cross all threetypes of networks.

Running test calls in a suitable test environment to evaluate new systemcomponents or functional upgrades of existing network infrastructure isoften prohibitively expensive and may be practically unfeasible. Forinstance, assume it is desired to run a test call for a call serviceevaluation that would simulate a call originated from a terminal of PSTNaccess network 110 to a cellular telephone user terminated in RAN 145.In this instance, a test environment would require PSTN access networkinfrastructure, a Class 4 switching apparatus interfaced with anotherClass 4 or Class 5 switching apparatus, and a wireless media gateway. Itis readily apparent that the logistics and monetary costs of deployingsuch a test environment are undesirable. However, deployment of asoftware package or product without thorough testing in a realisticnetwork environment is undesirable.

FIG. 2 is a diagrammatic representation of at least a portion of anetwork 200 in which a test call may be evaluated in a conventionalmanner. In the present example, a test call representative of a calloriginating from a wireless terminal to a wireline terminal is depicted.A call originates at a calling party that interfaces with a mediagateway 210 and is destined for a called party that interfaces with amedia gateway 240. In the present example, media gateway 210 isinterconnected with a wireless network 220 that is, in turn,interconnected with a wireline network 230, such as the PSTN, via apacket network 250. Wireless network 220 may included various wirelessnetwork infrastructure, such as media gateways 221-222, and wirelinenetwork 230 may include various network infrastructure, such as mediagateways 231-232. A realistic evaluation or test of bearer parametersand service features of end-to-end calls in such a service scenariowould require deployment of four media gateway in a suitable testenvironment. Deployment of such a test environment by, for example, atelecommunication product vendor is undesirable.

In accordance with embodiments disclosed herein, a mechanism foremulating a network for testing and performance modeling is provided.Network emulation mechanisms disclosed herein provide for significantcost savings and facilitate development of robust network components inan economically and logistically feasible manner. In another embodiment,resources that are utilized for testing purposes do not requirededicated allocation for such purposes but, rather, may be shared withother applications. In other embodiments, emulation mechanisms areprovided that allow for testing a part of a network in a highlyconfigurable way such that different network configurations anddifferent call characteristics with varying attributes may be evaluated.

In particular, a mechanism is provided for using a single media gatewayand a gateway controller to emulate a wireless, wireline, and/or packetnetwork in accordance with embodiments disclosed herein. A single mediagateway, a media gateway controller, and a network emulation and testdriver module (also referred to herein as a network emulator) are usedto emulate a converged network for testing calls, call features, andnetwork performance characteristics. The media gateway is used toemulate a converged network by providing bearer connections betweeninterfaces of different network types with termination ports ofdifferent bearer characteristics. A media gateway controller providescall behaviors and control messages to the media gateway to implementnetwork emulation. The network emulator is responsible for driving theemulation of a converged network and for driving test calls through theemulated network.

FIG. 3 is a diagrammatic representation of a configuration 300 ofinterconnections between a media gateway 310, a media gateway controller320, and a network emulator 330. Network emulator 330 may be includedin, or otherwise interface with, MGC 320. Network emulator 330 monitorsfor a specific condition to trigger a test call. The test call may betriggered in parallel with other test calls, in parallel with non-testcalls, or in a single test call evaluation. For example, networkemulator 330 may detect a particular data element that is assigned orallocated for test call purposes. In one implementation, a data elementassigned for test call purposes may comprise a termination ID (TID). Thetermination ID may comprise an interface type, a group number, such as aspan number, and a member number, such as a channel number. In otherimplementations, a data element assigned or allocated for test callpurposes may comprise one or more other data elements, such as callingline identity (CLID), a called party telephone number, a calling partyor called party network address, or another suitable data element thatmay be designated for test call purposes. Once the condition isdetected, network emulator 330 provides a command that triggers callprocessing for the test call and causes the appropriate media controlmessages to be sent to the associated media gateway. From theperspective of media gateway 310, no distinction between a test call anda non-test call is required. That is, media gateway 310 processes a testcall as directed by media gateway controller 320, and the test callappears as a “normal” call to the media gateway. Pursuant to providing amechanism for emulating a converged network, MGW 310 may be configuredsuch that a single test call is conveyed thereto as multiple inbound andoutbound call traffic. In one implementation, feedback mechanisms aredeployed on MGW 310 for returning outbound traffic of a test call to MGW310 where the returned test call traffic is treated as a separate callby the MGW. In another implementation, test call traffic may beinternally switched, e.g., via a MGW bus, from one media interface toanother media interface to emulate multiple network components.

In accordance with embodiments described herein, normal call processingmay be leveraged to trigger insertion of bearer connections withtest-specific bearer attributes during call test procedures. Moreover,media gateway features may be tested in parallel with other test trafficand with normal call traffic processing by way of call evaluationsperformed by trigger-based mechanisms. A media gateway may be used toemulate a converged network comprising multiple types of networkcomponents such as wireless, wireline, such as PSTN, and packet, such asInternet protocol (IP), network components.

In accordance with embodiments disclosed herein, a media gateway may beconfigured to emulate a converged network to realistically test callsthat emulate traversal across multiple media gateways of a convergednetwork. Moreover, any number of bearer connections with any bearertypes and attributes may be applied to a test call thereby providing anefficient mechanism to verify features deployed on a media gatewaywithout using third-party MGC software. An arbitrary number of bearerconnections with specific parameters may be inserted into acommunications path that is otherwise conventionally allocated betweentwo terminations across multiple media gateways. The insertion of bearerconnections is triggered by the normal call processing function of a MGCwhen an originator's termination ID (or other data element) matches aTID (or other data element) allocated for test scenarios. A TIDallocated for a test scenario may be referred to herein as a triggertermination or trigger TID. A test call comprises a trigger terminationand a list or other data structure of bearer connections to be appliedto the test call. Each bearer connection may be configured with specificbearer attributes.

FIG. 4A is a diagrammatic representation of an embodiment of a mediagateway 400 that may be configured to emulate a converged network formedia gateway and call testing. Media gateway 400 may include interfacescapable of connecting to wireless networks, packet networks, wirelinenetworks, and/or other network systems, and each of the interfaces maybe used to emulate a particular network type to facilitate realistictesting of connections and handoff between different types of networks.

Media gateway 400 comprises a converged media gateway. As referred toherein, a converged media gateway refers to a gateway adapted orotherwise configured to handle traffic—signaling and/or payload—of aplurality of network types, such as wireline, packet, and wirelesstraffic. To this end, media gateway 400 comprises three generalinterface card types: packet, wireline, and wireless interface cards. Inthe illustrative example, media gateway 400 includes wireline, e.g.,PSTN, interface (I/F) cards 420 a-420 b, packet interface cards 421a-421 b, and wireless interface cards 422 a-422 b the latter of whichprovides a packet interface to a wireless network

In the illustrative example, media gateway 400 comprises a switchingmedia gateway adapted to provide switching services. To this end, mediagateway 400 includes two switching matrixes 430 a-430 b. In the presentexample, switching matrix 430 a comprises a TDM switching matrix, andswitching matrix 430 b comprises a packet switching matrix.

TDM switching matrix 430 a switches voice channels between TDM networkinterface cards 420 a-420 b and a service module 440. Packet switchingmatrix 430 b switches packet channels between packet interface cards,such as interface cards 421 a-421 b, and service module 440. Packetswitching matrix 430 b may be implemented as an Ethernet or other packetswitching fabric that may be capable of switching traffic between portsof packet-capable interfaces, such as ports of interface cards 421 a-421b. In one exemplary implementation, packet switching matrix 430 b may beimplemented using a gigabit Ethernet switching fabric, such as thosemanufactured by Broadcom Corporation or Marvel Technology Group Limited.The specific implementation for switching matrix 430 b may be selectedbased on design choice, the number of ports required by media gateway400, or other factors.

Service module 440 may comprise various functional modules for handlingvarious types of data types and formats. For example, service module 440may include various voice chips, such as VoIP chips, voice-over-ATMadaptation Layer-1 (AAL1) chips, and voice-over-AAL2 chips, forprocessing of various voice data. For example, a VoIP chip deployed onservice module 440 provides IP packetization of voice data, andvoice-over-AAL1 and AAL2 chips provide segmentation and reassemblyfunctions of various voice formats to or from ATM cells. In addition,each voice server includes digital signal processors (e.g., voicetranscoders or Codecs, echo cancellers, conference bridges, etc.), atime slot interconnection (TSI), and a central processing unit (CPU).One or more voice chips may implement one or more VoIP protocols, suchas Real time Transmission Protocol (RTP). In addition to various Codecs,conference bridges, echo cancellation functions, service module 440 mayprovide conversion between data in one packet format and data in anotherpacket format, and between non-packetized, e.g., TDM, data to/from apacket format.

Packet switch matrix 430 b may be connected to packet interfaces, suchas ATM and IP interfaces. Media gateway 400 may be adapted to handlevarious packet formats. In the illustrative example, media gateway 400is adapted to process packet data formatted in accordance with IP andATM, although other packet formats may be supported in lieu of, or inaddition to, IP and ATM. The depiction of media gateway 400 adapted tosupport IP and ATM formats is provided for illustrative purposes onlyand is chosen to facilitate an understanding of embodiments disclosedherein. IP network interfaces, such as interface cards 421 a and 422 b,each include functionality for sending and receiving media packets, suchas voice packets, over IP. An interface of one packet format, such asATM or IP, may be adapted to support connection to either a wireless orwireline network. For example, IP interface card 421 a and 422 b arerespectively adapted to connect to a wireline IP network and a wirelessIP network.

FIG. 4B is a diagrammatic representation of a logical configuration ofmedia gateway 400 for emulating a converged network. In the illustrativeexample, media gateway 400 is configured with termination points 460-462(illustratively designated X1-X3). Termination points 460-462 providefor emulation of a converged network having three media gateways. A testcall may then be routed from one termination point to anothertermination point to emulate a call routed between media gateways ofdifferent networks.

A call generator 475 generates a test call that is conveyed totermination point 460 of media gateway 400. Call generator 475 may, forexample, be implemented as a telephone or other communication devicecommunicatively coupled with media gateway 400. Call generator 475 maybe coupled with media gateway 400 by a local loop or other suitableinterconnection. The test call is then routed from termination point 460to termination point 461 and, in turn, from termination point 461 totermination point 462. In the illustrative example, the test call isthen routed to a call terminator 476. Thus, the call origination fromcall generator 475, routing between the various termination points, andtransmission of the call to a call terminator 476, may emulate a callrouted through three media gateway. Call terminator 476, like calloriginator 475, may be implemented as a telephone or other communicationdevice communicatively coupled with media gateway 400. In thisillustrative example, a test call delivered from call generator 475 tomedia gateway 400, through termination points 460-462, and to callterminator 476 exhibits call characteristics and behaviors of a callthat is routed through four distinct networks—one emulated networkbetween call generator 475 and termination point 460 of media gateway400, one emulated network represented by the outbound delivery of thetest call from termination point 460 to termination point 461, oneemulated network represented by the outbound delivery of the test callfrom termination point 461 to termination point 462, and a finalemulated network represented by the outbound transmission of the testcall from termination point 462 to call terminator 476.

Any variety of bearer characteristics or services may be applied on aconnection between termination points, and a connection betweentermination points may be implemented in accordance with any networktype supported by media gateway 400. In this manner, receipt of a testcall formatted according to one network type at a termination point, andsubsequent transmission of the call at the termination point, or anothertermination point, in a different network format provides for emulationof a call handoff from one network type, e.g., from a wireless network,to another network type, e.g., to a packet network.

With reference now to FIG. 4C, a diagrammatic representation of anembodiment of media gateway 400 depicted in FIG. 4B is shown in aphysical configuration for emulating a test call. In the presentexample, media gateway 400 is depicted in a configuration for emulatinga call routed among four networks. Media gateway 400 includes variousinterface cards 480 a-480 f. In the present example, interface cards 480a-480 b comprise wireline TDM interface cards, interface cards 480 c-480d comprise packet interfaces implemented as wireline ATM interfacecards, and interface cards 480 e-480 f comprise wireless IP interfacecards. Media gateway 400 may be equipped with any number of interfacecards of various network transmission types, and those shown are onlyillustrated to facilitate an understanding of embodiments disclosedherein.

In the illustrative example, interface cards 480 a-480 b are connectedwith service module 440 via an interconnect 470 a, and interface cards480 c-480 f are connected with service module 440 via an interconnect470 b. In a similar manner, interface cards 480 a-480 b are connectedwith TDM switch matrix 430 a via a suitable interconnect 470 c, andinterface cards 480 c-480 f are connected with packet switch matrix 430b via an interconnect 470 d. The configuration of interface cards 480a-480 f and interconnects with service module 440 and switch matrices430 a and 430 b are illustrative only. For example, each of interfacecards 480 a-480 f may share a common interconnect with service module440 or, alternatively, each of interface cards 480 a-480 f may each havea respective interconnect with service module 440. Interconnects 470a-470 d may be implemented as, for example, one or more internal busesdeployed on a backplane of media gateway 400.

Interface cards 480 a-480 f may each include one or more respectivephysical ports 481 a-481 f. Interface cards 480 a-480 f may comprise aplurality of physical ports, and a single port is shown on each ofinterface cards 480 a-480 f to simplify the illustration. Media gateway400 may be configured for a test call evaluation by coupling one or moreports of one or more interface cards to provide call feedback to mediagateway 400. In the present example, physical port 481 c of interfacecard 480 c is connected with physical port 481 d of interface card 480 dvia a communication coupling 492, such as a conductive cable. In asimilar manner, physical port 481 e of interface card 480 e is connectedwith physical port 481 f of interface card 480 f via a communicationcoupling 493.

A test call is generated by call generator 475 and conveyed to mediagateway 400. In the illustrative example, a test call comprising adigital signal 0 (DS0) is generated by call generator 475 andtransmitted to media gateway 400 via a communication medium 490, such asa T-carrier copper medium. The test call may be multiplexed on medium490 and thus may be assigned a particular logical designation or channelassignment. In the illustrative example, the test call is carried on achannel allocated on medium 490 with a channel designation of “DS0 Group1”. On receipt of the test call by media gateway 400 at TDM interfacecard 480 a, the test call may be conveyed to service module 440 viainterconnect 470 a. In the present example, assume that media gateway400 processes the test call for transmission out media gateway 400 overa cell relay wireline network. In this instance, the test call may beencoded into ATM cells and thereafter conveyed to packet switch matrix430 b. Assume packet switch matrix 430 b switches the ATM-formatted testcall to wireline ATM interface card 480 c for transmission out port 481c. In the present example, the ATM-formatted test call is output with adesignation of “AAL2 Group 1”. In this instance, the ATM-formatted testcall is fed back to port 481 d of wireline ATM interface card 480 d viacoupling 492. Notably, media gateway 400 does not recognize the testcall as associated or otherwise related to the ATM test call output frominterface card 480 c. That is, from the processing perspective of mediagateway 400, the test call that is fed back to media gateway 400 atinterface card 480 d appears to media gateway 400 simply as an inboundcall received over a packet network. In the present example, the testcall presented as inbound traffic at interface card 480 d via feedbackcoupling 492 is designated “AAL2 Group 2”.

The ATM-formatted test call may then conveyed to service module 440 viainterconnect 470 b. Assume that media gateway 400 processes theATM-formatted test call for transmission over a wireless IP network. Inthis instance, the cells of the ATM-formatted test call are reassembledand then packetized into a suitable packet format, e.g., InternetProtocol (IP) packets. The packetized test call may thereafter beconveyed to packet switch matrix 430 b. Assume packet switch matrix 430b switches the packetized test call to wireless IP interface card 480 efor transmission out port 481 e. In the present example, the packetizedtest call transmitted out interface card 480 e has a designation “IPGroup 1”. In this instance, the packetized test call is fed back to port481 f of wireless IP interface card 480 f via feedback coupling 493. Ina similar manner as that described for the ATM feedback, media gateway400 does not recognize the inbound packetized test call received atinterface card 480 f as associated or otherwise related to the test calloutput from interface card 480 e. The test call that is fed back tomedia gateway 400 at interface card 480 f appears to media gateway 400simply as an inbound call received over a packet network. In the presentexample, the test call presented as inbound IP traffic at interface card480 f via feedback coupling 493 is designated “IP Group 2”. Thepacketized test call may then be conveyed to service module 440 viainterconnect 470 b.

Assume that media gateway 400 processes the packetized test call fortransmission over a TDM network. In this instance, the packets of thetest call are reassembled and formatted for TDM transmission, e.g.,formatted into an 8 kHz voice-frequency signal for transmission as a DS0signal. The TDM test call is thereafter conveyed to TDM switch matrix430 a. Assume TDM switch matrix 430 a switches the TDM test call towireline TDM interface card 480 b for transmission out port 481 b. TheTDM test call is then transmitted to call terminator 476 viacommunication medium 491. In the illustrative example, the TDM test calloutput from media gateway 400 via interface card 480 b has a logicaldesignation or channel assignment of “DS0 Group 2”.

In the example described in FIG. 4C, processing of the test callemulates a call transmitted over four networks having three distinctnetwork types. Particularly, transmission of the test call from callgenerator 475 to media gateway 400 emulates a call transmission over aTDM network to a first media gateway. Subsequent transmission of thetest call out wireline ATM interface card 480 c, over coupling 492, andto wireline ATM interface card 480 d emulates a call routed from thefirst media gateway to a second media gateway over a wireline ATMnetwork. In a similar manner, transmission of the test call fromwireless IP interface card 480 e to wireless IP interface card 480 f viacoupling 493 emulates a call transmission from the second media gatewayto a third media gateway over a wireless IP network. Transmission of thetest call from TDM interface card 480 b to call terminator 476 overcommunication medium 490 emulates a call transmission from the thirdmedia gateway over a TDM network. Thus, the configuration of mediagateway 400 depicted in FIGS. 4B and 4C provides for emulation of calltransmission over a converged network including TDM, ATM, and wirelessIP infrastructure.

Media gateway 400 may be configured to emulate a converged network forcall processing evaluation with minimal hardware adaptation. In theillustrative example, media gateway 400 is physically configured for theabove described test call scenario by simply coupling ports of interfacecards 480 c-480 d and 480 e-480 f. In this manner, the test callsupplied to media gateway 400 for call processing evaluation appears tothe media gateway hardware as any other “normal” call. That is, mediagateway processes and switches the test call in accordance with normalcall switching mechanisms and is not aware that the test call is fedback to media gateway 400. For example, when media gateway 400 receivesthe test call at port 481 d from the feedback mechanism, media gateway400 only recognizes the test call as incoming call at card 480 d anddoes not require any special hardware or software switching orprocessing adaptation for handling the test call. In a similar manner,when media gateway 400 receives the test call inbound at interface card480 f, media gateway 400 treats the test call as a normal inbound call.

It should be understood that the particular media gateway configurationdepicted in FIG. 4C is illustrative only, and other configurations ofmedia gateway 400 for emulating a converged network may be implemented.For example, a feedback mechanism may be terminated at two ports of acommon interface card thereby reducing the requisite hardware foremulating a converged network. In such a configuration, a call may betransmitted out of a network interface card over a feedback coupling andsubsequently received by the same interface card over the feedbackcoupling.

In other implementations, a media gateway may not require a physicalfeedback mechanism for implementing one or more embodiments disclosedherein. For example, multiple termination points may be specified foremulating a plurality of packet networks. In this instance, a packetizedtest call may be conveyed from packet switch matrix 430 b to a packetinterface card, and the packet interface card may return the packetizedtest call to a VoIP chip of service module 440. The packetized test callmay then be processed for transmission over another emulated packetnetwork, and may accordingly be transmitted to another (or the same)packet interface card. In this scenario, two termination points andtransmission of a call therebetween may be made on a single mediagateway without the use of a physical feedback mechanism.

FIG. 4D is a diagrammatic representation of a converged networksimulated by the configuration of media gateway 400 shown in FIGS. 4Band 4C. In the present example, media gateway 400 depicted in FIG. 4B isconfigured to represent three simulated media gateways 400 a-400 c for atest call that simulates a call that is routed through four networks. Inthe present example, the test call provides a simulation of a callrouted through a simulated wireline TDM network 410 to a media gateway400 a, through a simulated wireline ATM network 411 via media gateways400 a and 400 b, through a simulated wireless IP network via mediagateways 400 b and 400 c, and through a simulated wireline TDM networkfrom media gateway 400 c. The coupling of interface cards 480 c and 480d via ports 481 c and 481 d via coupling 492 provides an effect of aconnection between media gateways 400 a and 400 b over simulatedwireline ATM network 411. In a similar manner, the coupling of interfacecards 480 e and 480 f via ports 481 e and 481 f and communication medium493 provides an effect of a connection between media gateways 400 b and400 c over simulated wireless IP network 412.

Each of the simulated media gateways 400 a-400 c and simulated wirelineand wireless networks 410-413 are emulated by the configuration of mediagateway 400 depicted in FIGS. 4B and 4C. Thus, media gateway 400advantageously provides a realistic test environment of a convergednetwork and provides an effective platform for call processing androuting evaluation.

In accordance with embodiments disclosed herein, a configuration file orother data structure is associated with a call parameter, such as a TID,and defines a particular test call routing and bearer scenario. Testcall triggers are defined to specify particular test call handling. Forexample, a configuration file that defines the test call depicted anddescribed in FIGS. 4B and 4C includes instructions that define contextsfor each of the TDM, ATM, and IP call routes. In this manner, anydesired test call scenario may be defined in a configuration file andprocessed by media gateway 400 assuming the test call scenario iscompliant with the supported network type and protocol set capabilitiesof media gateway 400.

FIG. 5 is a diagrammatic representation of a configuration of mediagateway controller 320 depicted in FIG. 3 that facilitates convergednetwork emulation in accordance with embodiments disclosed herein. MGC320 may include one or more of various functional entities, such as,among others, a softswitch, a subscriber profile module 510, a callmanager 520, a signaling gateway module 530, and a facility resourcemanager 540.

Subscriber profile module 510, or a subscriber profile manager function,may be configured to retrieve subscriber data for validation, e.g., atcall origination and termination. To this end, subscriber profile module510 may interface with a subscriber database 570. Subscriber profilemodule 510 may also, or alternatively, be configured to provide aframework for subscriber feature deployment and/or an applicationprogramming interface (API) for efficient application development anddeployment. An evolution path to off-board advanced intelligent network(AIN) triggers may also, or alternatively, be provided by subscriberprofile module 510. Subscriber profile module 510 may be associated withsubscriber database 570 to directly retrieve subscriber and associatedservice feature information. Subscriber profile module 510 may belocated on a dedicated, stand-alone data processing system, or may beintegrated with additional functions or apparatus.

Call module 520, or a call manager function, may be configured toprovide a generic, trigger-based, state-machine driven call model and tosupport distributed call processing. Call module 520 may be independentof external physical signaling interfaces and protocols, and may beconfigured to handle a variety of bearer traffic. In one embodiment, asystem or network may have a minimum of two instances of call manager520 to provide for call manager function fault tolerance. Someembodiments may not require or otherwise include a fixed association ofa defined ratio between channels and the number of instances of callmodule 520. Call module 520 may also, or alternatively, facilitate orotherwise support call traffic distribution across all in-serviceprocesses or functions, and/or may be configured to provide or supportcall preservation, e.g., through evaluation of critical call informationat call ringing and stable call states. Call manager 520 may be deployedon a dedicated, stand-alone processor or data processing system or,alternatively, may be integrated within a data processing system ortelecommunications node that provides other functionality in addition tocall manager functionality.

Signaling gateway module 530, or a signaling gateway manager function,may be configured to support Point Code operations, and may also, oralternatively, be configured to provide or support fault tolerance.Signaling gateway module 530 may comply with, enable compliance with, orotherwise support ITU standards, ANSI signaling standards, SIP,Megaco/H.248 and/or other gateway control protocols. Signaling gatewaymodule 530 may be deployed on a dedicated, stand-alone processor or dataprocessing unit or, alternatively, may be integrated with a dataprocessing system or node that provides other functionality in additionto signaling gateway manager functions.

Facility manager 540 may be configured to provide trunk and lineallocation service for call processing, handle non-call-associatedsignaling (e.g., an ISUP BLO messaging), and/or process requests toremove trunks or lines from service due to faults or manualintervention. Facility manager 540 may also, or alternatively, beconfigured to process requests regarding out-of-service trunks or linesand return the trunks or lines to service.

MGC 320 manages one or more media gateways 400 via any variety ofstandard protocols, such as MEGCO (Media Gateway Control), or otherstandard or proprietary protocols. In addition, MGC 320 may be connectedto one or more application servers 550 to provide services like E911,CALEA and others. To facilitate emulation of a converged network withMGW 400, network emulator 330 may be deployed on MGC 320 and mayinterface with a network emulation configuration file store 340. Networkemulation configuration file store 340 may include one or moreconfiguration files 340 a-340 n that each respectively define a testcall. For example, configuration files 340 a-340 n may each definerouting, encoding, transport, and other characteristics of a particulartest call scenario. Each of configuration files 340 a-340 n may beassociated with, or include, a particular data element that facilitatesrecognition of a test call by MGC 320. In the present example, each ofconfiguration files 340 a-340 n each include, or are otherwiseassociated with, a respective TID (illustratively designatedTID_a-TID_n).

FIG. 6 is a diagrammatic representation of an exemplary call signalingflow among a MGW and various MGC components or functions thatfacilitates call set-up. Messages exchanged between a media gateway andthe call manager may be either call control messages or media gatewaycontrol message, such as MGCP. In response to detecting a subscriberthat has gone offhook, the MGW sends a Set-up message 602 that comprisesa call control message to the call manager. The Set-up message signalsthe call manager that a subscriber phone has gone offhook. AnOrigination Attempt message 604 may then be generated and transmittedfrom the call manager to the facility manager that, in turn, relays theOrigination Attempt to the subscriber manager. The subscriber managermay then evaluate the origination attempt, e.g., interrogate subscriberdatabase 570. Assuming the originator is a valid subscriber, thesubscriber manage may return a Continue message 608 to the call managerthat, in turn, generates and sends an “Add” message 610 to the MGW.Continue message 610 may include one or more subscriber data elements,such as a TID of the call originator that may be evaluated fordetermining whether the call is a test call. The Add message 610 maycomprise a MGCP message that instructs the media gateway to create aswitch context, apply a dial tone to the appropriate phone line, andprepare for collecting digits from the phone line. A “Digits” message612 is sent from the MGW to the call manager and comprises a callcontrol message that includes the collected dialed digits. A terminationattempt message 614 may then be generated by the call manager and sentto the facility manger. The facility manger may then send an AuthorizeTermination message 616 to the call manager. The call manager may thengenerate and send an Add message 618 to the MGW that instructs the mediagateway to add the outside trunk line to the context. The call mangermay additionally generate and send a Set-up message 620 to the signalinggateway that instructs the signaling gateway to proceed with call set-upwith the dialed party. The signaling gateway may then generate and sendan Alerting message 622 to the call manger that notifies the callmanager that the called party is being alerted. Assuming the calledparty answers the call, the signaling gateway may generate and send anAnswer message 624 to the call manager when the called party goesoffhook. In response to receipt of the Answer message, the call mangermay generate and send a Modify message 626 to the MGW. The Modifymessage may comprises a MGCP message that instructs the media gateway toconnect a bearer voice path between the phone line of the called partyand an outside trunk to complete call establishment.

FIG. 7 is diagrammatic representation of a configuration of networkemulator that drives network emulation and testing in accordance withembodiments disclosed herein. Network emulator 330 may be deployed orotherwise interface with MGC 320 depicted in FIG. 3. Network emulator330 may include a command monitor 710 that monitors for particular testevents. In accordance with embodiments disclosed herein, test events maybe recognized by test “triggers” associated with a test call.Recognition of a test trigger by command monitor 710 provides anidentification of a call as a test call. Command monitor 710, inresponse to recognition of one or more test triggers, may then respondto the test trigger event by invoking one or more test call proceduresor routines of network emulator 330.

In accordance with an embodiment, a particular termination identifier(TID), referred to herein as a trigger TID, may be allocated for testcall purposes. Command monitor 710 may monitor the TIDs of incomingcalls. In the event that a TID of an incoming call matches a predefinedtrigger TID allocated for test purposes, command monitor 710 identifiesthe incoming call as a test call and may then invoke test call functionsaccordingly. As noted above, another data element may be allocated fortest call purposes, and the description of a TID for use as a test calltrigger invocation is provided to facilitate an understanding ofembodiments disclosed herein.

Network emulator 330 may include a control module 720 that may beinterfaced with command monitor 710. Additionally, network emulator 330may include a command parser 740 that is interfaced with control module720. Command parser 740 is additionally configured to retrieve a callconfiguration file (CF) 340 a-340 n from configuration file store 340and parse commands included in the retrieved configuration file.Configuration file store 340 comprises a storage, such as a database orfile storage maintained on a hard disk, memory device, or other suitablestorage medium, that maintains a set of call configuration files 340a-340 n. Each of configuration files 340 a-340 n may be associated witha particular test call routine. For example, each of configuration files340 a-340 n may include, or otherwise be associated with, a particularpredefined TID, or other suitable data element, allocated to a test callscenario. Additionally, command parser 740 may be configured totranslate commands contained in a configuration file into a formatsuitable for processing by call manager 520. Command parser 740 may beinterfaced with control module 720 for transmitting parsed call commandsand parameters thereto. Control module 720 may be adapted to generatecall control messages according to the call commands received thereby,and transmit the generated call control messages to a media gateway.

Network emulator 330 may be invoked independently or in conjunction witha MGC. In the latter case, a command line interface parameter or othersuitable mechanism may be configured for a user to invoke networkemulator 330.

Each configuration file 340 a-340 n defines a set of connections betweentermination points within a media gateway though which a test call is tobe conveyed, behaviors of the test call during transmission acrosstermination point connections, and associated bearer parameters andservice features. In this manner, a configuration file 340 a-340 ndefines end-to-end characteristics of the test call.

Configuring test call characteristics by way of configuration files 340a-340 n provides for a highly flexible and configurable test callconfiguration mechanism as opposed to other options, such as hard codinga call testing route. In this manner, various network connections andconditions may be emulated by any variety of configuration files 340a-340 n.

In accordance with an embodiment, a configuration file may have avariable number of specifiers that each defines one aspect of a testcall. The particular number of specifiers may depend on the particulartest call scenario that is defined by the configuration file.

In one implementation, the syntax of each specifier comprises a headerwith one or more parameters appended thereto. In an exemplaryembodiment, specifiers defined in a configuration file may include: amapping specifier, a termination specifier, and a media parameterspecifier. Other specifiers, such as an event specifier that definesevent time outs, may be included as well.

A mapping specifier defines a mapping between a physical and logicalresource. In accordance with an embodiment, the mapping specifier isdenoted by a header “M”. The mapping specifier defines alogical-to-physical media gateway facility number mapping and, in anexemplary implementation, has the form:M<logical, physical>

-   -   where logical comprises a parameter value that specifies a        logical media gateway facility number. The logical media gateway        facility number may be specified as an integer value within a        predefined range, e.g., 1-31. The physical parameter value may        comprise an actual media gateway facility ID number. In the        event that no mapping exists, the parameter of the mapping        specifier may be interpreted as a physical ID.

A termination specifier defines a termination ID identifying atermination point at the media gateway for making a physical connection.In an exemplary embodiment, the TID may comprises an interface type, agroup number (such as a span number), and a member number (such as achannel number). The termination specifier may be denoted by a header“T” An exemplary termination specifier format is as follows:T<Node#, If_Type, Group, Member>

Node# is an optional parameter that comprises a value specifying alogical or physical media gateway node number. The If_Type parametervalue defines an interface type. Example parameter values of If_Type mayinclude: DS0_IF, AAL1_TRUNK_IF, AAL2_TRUNK_IF, VOIP_TRUNK_IF, AAL2_IF,UMTS_AAL2_IF, or any other suitable interface type. The Group parametercomprises a non-zero integer value that specifies a link, such as aT1-span number or other identifier. The Member parameter comprises avalue selected from an available range, e.g., 1-4, 8-12, that may definea channel of the group. For example, the Member parameter may define achannel number or the mechanism for channel selection. Exemplary Memberparameter values may be defined as follows:=“0”; the media gateway controller selects the test call channel=“−1”; unspecified, media gateway selects the test call channel=“−2”; loopback, use same channel as preceding termination=“−3” loopback, use same channel as trigger termination

An example of a termination specifier is as follows:T<DS0_IF, 3701, 0>, <AAL2_IF, 8, −1>, <1, VOIP_TRUNK_IF, 10, −1>

In accordance with one embodiment, a first TID defined in aconfiguration file comprises the trigger TID for the configuration fileand is allocated for test call purposes. If an origination terminationID matches the first TID defined in a configuration file, test callprocedures may be invoked, and a test call is executed according to theconfiguration file. A TID allocated for test call purposes may comprisean If_Type, a Group, and a Member of a configuration file. In the eventthat a call originator's TID matches a TID of a configuration file,other terminations defined in the configuration file may be added to thecall with parameters specified in the configuration file.

The media parameter specifier may define media bearer parameters. Themedia parameter specifier may include a header, such as “P”. Anexemplary media specifier format is as follows:P<Descriptor [param1 (value) param2 (value) param3 (value) . . . ]>where the Descriptor has one or more parameter values that may specifycall descriptions such as LOCAL_DESCR for local call description,DS0_RX_DESCR for a DS0 based call descriptor, AVD_RX_DESCR,UMTS_RX_DESCR, UMTS_CTM_DESCR for UMTS and CTM call types,TFO_LOCAL_DESCR, other bearer characteristics, service features, and thelike.

Descriptor parameter (param) values may be, for example, assigned avalue according to the following:

-   -   1. enumeration (e.g., UMTS_UP_MODE_TRANS)    -   2. decimal (e.g., 2)    -   3 hexadecimal (e.g., 0×45)

In one embodiment, Descriptor parameter values may be specified in aparticular order. Parenthetical values following an enumeration with avalue may be ignored. If a parameter value is not present, default (0)may be interpreted for the parameter value.

In accordance with an embodiment, multiple test routes may be supported.Multiple routes may be separated or otherwise designated with adelimiter, such as a “−” or other suitable character. Additionally,termination and media parameter specifiers may be delimited with a newline in the configuration file. Multiple media parameter specifiers maybe specified per termination Identifier to support different controlprotocol descriptors.

An exemplary configuration file for emulating the test call discussedabove with reference to FIGS. 4B and 4C is as follows:

Line1 # Map logical MGW node 1 to physical MGW node 7, and Line 2 # Maplogical MGW node 2 to physical MGW node 8 Line 3 M<1, 7> Line 4 M<2, 8>Line 5 # First Context - TDM (trigger termination) to AAL2 Line 6T<DS0_IF, 3701, 0> Line 7 T<AAL2_IF, 9, 0> Line 8 P<UMTS_CTM_DESCR [UMTS_CTM_PREPARE (2) Line 9 UMTS_TEXT_TRANSPORT_CTM (8)UMTS_TEXTPROT_VER_1 (1) 0]> Line 10 P<AVD_RX_DESCR [ EC_128 EC_NO ]>Line 11 # Second Context - AAL2 to VOIP Line 12 #T<AAL2_IF, 10, −2> Line13 T<1, VOIP_TRUNK_IF, 2700, −1> Line 14 P<UMTS_RX_DESCR [UMTS_UP_MODE_SUPP UMTS_UP_VERSION_2 Line 15 UMTS_DEL_ERRSDU_YESUMTS_UP_INTF_TYPE_NB Line 16 UMTS_UP_INIT_DIR_OUT INHIBIT_TRFO_NO { 0x860xff 0xff 0 8 } ]> Line 17 #Third Context - VOIP to TDM (finaltermination) Line 18 T<2, VOIP_TRUNK_IF, 2900, −1> Line 19P<UMTS_RX_DESCR [ UMTS_UP_MODE_SUPP UMTS_UP_VERSION_2 Line 20UMTS_DEL_ERRSDU_YES UMTS_UP_INTF_TYPE_NB Line 21 UMTS_UP_INIT_DIR_ININHIBIT_TRFO_NO { 0x86 0xff 0xff Line 22 0 8 } ]> Line 23P<UMTS_CTM_DESCR [ UMTS_CTM_PREPARE (2) Line 24 UMTS_TEXT_TRANSPORT_CTM(8) UMTS_TEXTPROT_VER_1 (1) 0 ]>

Line numbers are included to facilitate a discussion of the exemplaryconfiguration file. In the present example, a mapping specifier M<1, 7>provided on Line 3 provides an association of a logical media gateway of“1” to a media gateway with a facility ID of “7”. In a similar manner, amapping specifier of M<2, 8> provided on Line 3 provides an associationof a logical media gateway of “2” with a media gateway having a facilityID of “8”.

Next, the configuration file includes various statements that define afirst call context at lines 5-10. In the illustrative example, Line 6specifies that the test call is inbound on a DS0 interface on a linkwith a group number “3701”. The termination specifier member parametervalue “0” indicates that the media gateway controller selects the testcall channel. The termination specifier parameters DS0_IF, 3701, and 0comprise a trigger TID that is allocated for test call purposes, and amatch between the trigger TID defined by the termination specifiers ofLine 6 in the example configuration file with a call originator's TIDresults in invocation of test call procedures described herein inaccordance with an embodiment. The termination specifier of Line 8specifies that the test call is to be routed out of the media gateway onan ATM interface with a group value “9” and that the particular channelon which the test call is to be transmitted outbound from the mediagateway is to be selected by the media gateway controller. Lines 8-10define media parameter specifiers that define various media bearerparameters or characteristics of the test call for transmission outboundfrom the trigger termination. In the present example, the mediaparameter specifier of the first test call context specifies that thetest call is to be transmitted in accordance with the UMTS standard andvarious characteristics thereof. First and second termination pointsspecified by respective termination specifiers of lines 6 and 7, and thebearer characteristics specified by lines 8-10, provide forconfiguration of a connection between the two termination points andthus provide for emulation of a connection between two networks, namelya TDM and ATM network.

Next, the configuration file includes various statements that define asecond call context at lines 11-16. In the illustrative example, thesecond call context comprises an inbound ATM call to voice over IP(VoIP) as specified at line 11. Line 12 specifies that the test call isinbound on an ATM interface with a group number “10”. The terminationspecifier member parameter value “−2” indicates that the inbound testcall channel of the second call context is the same as the previoustermination. That is, the termination specifier member parameterindicates that the ATM test call is fed back on the same channel as theoutbound ATM test call of the first termination. The terminationspecifier of Line 13 specifies that the test call is to be routed out ofthe media gateway having a node number “1” on a VoIP trunk interfacewith a group number “2700”, and that the particular channel on which thetest call is to be transmitted outbound from the media gateway is toselected by the media gateway. Lines 14-16 include media parameterspecifiers that define various media bearer parameters of the test callfor transmission outbound from the media gateway. In the presentexample, the media parameter specifier of the second test call contextspecifies that the test call is to be transmitted in accordance with theUMTS standard and various characteristics thereof. Termination pointsspecified by respective termination specifiers of lines 12 and 13, andthe bearer characteristics specified by lines 14-16, provide forconfiguration of a connection between the two termination points andthus provide for emulation of a connection between two networks—in thisinstance, an ATM network and a wireless packet network.

Next, the configuration file includes various statements that define athird call context at lines 17-24. In the illustrative example, thethird call context comprises an inbound VoIP to outbound TDM call asspecified at line 17. Line 18 specifies that the test call is inbound tothe media gateway having a node number of “2” on a VoIP interface with agroup number “2900”. The termination specifier member parameter value“−1” indicates that the inbound test call channel of the second callcontext is selected by the media gateway. Lines 19-24 define variousmedia parameter specifiers that define various media bearer parametersof the UMTS test call.

FIG. 8 is a flowchart 800 depicting a high level flow of an embodimentfor emulating a converged network in accordance with embodimentsdisclosed herein. A call configuration file that defines the connectionsbetween termination points on a converged network for the call, bearerconnection characteristics and parameters, and possibly a call durationis defined (step 802). A test call is then generated to triggerexecution of the call defined in the call configuration file with aspecific TID (step 804). The configuration file is then interpreted todefine the test call behavior and call processing by the media gatewaycontroller as defined in the call configuration file (step 806). Thetest call is then executed step-by-step, terminationpoint-by-termination point as directed by the call controller on a mediagateway that emulates a converged network (step 808). It should beunderstood that various message exchanges may be made between a MGW anda MGC for carrying out the test call in accordance with theconfiguration file.

FIG. 9 is a flowchart 900 depicting call processing and call executionof a test call in an emulated converged network in accordance withembodiments disclosed herein. The processing steps of FIG. 9 generallydepict processing of steps 806 and 808 shown in FIG. 8. First, theconfiguration file is parsed (step 902), and the logical resource IDdefined in the call configuration file is translated into a physical ID(step 904). With the physical ID, a termination point is terminated(step 906), and a connection is then made with another termination pointon the media gateway (step 908). Then bearer parameters and services,such as transcoder free operation (TrFO) for a UMTS call, echocancellation for a VoIP call, adaptive multi-rate (AMR) compression, orthe like, are applied to establish the call (step 910), and the testcall may then be completed.

FIG. 10 is a flowchart depicting processing of a media gatewaycontroller for detection of a test call and processing thereof. Networkemulator 330 is invoked (step 1002), and a signaling message thatinstructs MGC 320 to set-up a call is generated (step 1004). MGC 320,responsive to receipt and processing of the call set-up message,allocates resources for the call (step 1005). For example, the callmanager 520 may negotiate with the facility manager to allocate afacility channel and/or other resources. Network emulator 330 may thenretrieve configuration file(s) 340 a-340 n from configuration file store340 (step 1006), and command monitor 710 may obtain the calloriginator's TID, or another suitable data element, for triggerevaluation (step 1008). On receipt of the call originator's TID, commandmonitor 710 may evaluate the TID to determine if it matches one of oneor more predefined TIDs allocated for test calls (step 1010). Forexample, command monitor 710 may compare the TID of the call originatorwith a respective trigger termination of configuration files retrievedin step 1006. If the TID is not evaluated as a TID allocated for testcalls, call set-up is processed in a conventional manner (step 1012),and the network emulator 330 cycle may end (step 1026).

Returning again to step 1010, in the-event that the call originator'sTID is evaluated as matching a predefined TID allocated for a test call,network emulator 330 may then generate call control messages accordingto the configuration file identified as having a TID that matches thecall originator's TID (step 1016), and the control messages are thensent to media gateway 310 (step 1018).

The media gateway, on receipt and processing of the control messages,may proceed with call set-up, including connecting with a particularport of a network interface specified in the configuration file,providing a dial tone and ringing signals as required by the call, andmay perform other set-up functions required to set-up the call. Themedia gateway may then send a connection status message to the mediagateway controller. On receipt of the connection status by networkemulator 330 (step 1020), network emulator 330 may begin monitoring forcall termination. For example, network emulator 330 may evaluate whethera user action, such as an on hook event, that terminates the test callhas occurred (step 1022). If a user action that terminates the test callis identified, the test call procedure may terminate according to step1026. If no user action that terminates the test call is identified atstep 1022, network emulator 330 may evaluate whether processing of thetest call has completed (step 1024). If the test call has not completed,the emulation routine may return to evaluate whether a user action hasoccurred that terminates the test call according to step 1022.Otherwise, the emulation routine may end according to step 1026.

The flowcharts of FIGS. 8-10 depict process serialization to facilitatean understanding of disclosed embodiments and are not necessarilyindicative of the serialization of the operations being performed. Invarious embodiments, the processing steps described in FIGS. 8-10 may beperformed in varying order, and one or more depicted steps may beperformed in parallel with other steps. Additionally, execution of someprocessing steps of FIGS. 8-10 may be excluded without departing fromembodiments disclosed herein. The illustrative block diagrams andflowcharts depict process steps or blocks that may represent modules,segments, or portions of code that include one or more executableinstructions tangibly embodied on a computer-readable medium forimplementing specific logical functions or steps in the process.Although the particular examples illustrate specific process steps orprocedures, many alternative implementations are possible and may bemade by simple design choice. Some process steps may be executed indifferent order from the specific description herein based on, forexample, considerations of function, purpose, conformance to standard,legacy structure, user interface design, and the like.

As described herein, a system, method, and computer-readable medium foremulation of a converged network with a single media gateway areprovided. In one embodiment, a method for emulating a converged networkincludes assigning a first termination point of a media gateway withcharacteristics of a first network, and assigning a second terminationpoint of the media gateway with characteristics of a second network. Aconnection between the first and second termination points isconfigured, and a call is transmitted from the first termination pointto the second termination point. In this manner, the connection betweenthe two termination points emulates a connection between two networks.In accordance with another embodiment, a method of emulating a convergednetwork comprises receiving, by a media gateway, a call at a firstinterface of a first network type. The call is processed fordistribution on a second network type. The processed call is transmittedto a second interface of a second network type. A service module of themedia gateway receives the processed call. In accordance with anotherembodiment, a method of emulating a converged network comprisingreceiving, by a media gateway controller, a call set-up message isprovided. A data element associated with the call set-up message isobtained, and a determination of whether the data element is allocatedfor a test call is made. A configuration file associated with the dataelement is retrieved that specifies one or more parameters of the testcall. Call control messages are generated according to the configurationfile, and the call control messages are transmitted to a media gateway.In accordance with another embodiment, a system for emulating aconverged network is provided. The system includes a media gatewaycontroller having a call generator and a network emulator respectivelyimplemented as computer-executable instructions, wherein the callgenerator generates a call that is transmitted by the media gatewaycontroller. The system includes a media gateway adapted to switchcommunications among a plurality of network types and is communicativelycoupled with the media gateway controller. The media gateway isconfigured with a plurality of network interfaces and may have afeedback mechanism for conveying the call from the media gateway back tothe media gateway. In accordance with another embodiment, acomputer-readable medium having computer-executable instructions forexecution by a processing system for facilitating converged networkemulation is provided. The computer-readable medium comprisesinstructions that monitor for a test event, and instructions that,responsive to detection of a test event, invoke a test call procedure.Instructions read a configuration file associated with the test event,and instructions generate one or more call control messages from theconfiguration file. The call control messages may then be transmitted toa media gateway.

Advantageously, a mechanism for implementing flexible test callevaluations is provided in which a single media gateway may be used foremulating a converged network. Implementations of embodiments disclosedherein provide effective emulation of call transmissions across aplurality of network types via a single media gateway. Any variety ofcall scenarios, including call transmissions across a plurality ofnetwork types, may be defined by respective configuration files, andrealistic testing of the call scenarios may be made with a single mediagateway. Accordingly, a realistic test environment may be implementedwith minimal network components.

Aspects of the present invention may be implemented in software,hardware, firmware, or a combination thereof. The various elements ofthe system, either individually or in combination, may be implemented asa computer program product tangibly embodied in a machine-readablestorage device for execution by a processing unit. Various steps ofembodiments of the invention may be performed by a computer processorexecuting a program tangibly embodied on a computer-readable medium toperform functions by operating on input and generating output. Thecomputer-readable medium may be, for example, a memory, a transportablemedium such as a compact disk, a floppy disk, or a diskette, such that acomputer program embodying the aspects of the present invention can beloaded onto a computer. The computer program is not limited to anyparticular embodiment, and may, for example, be implemented in anoperating system, application program, foreground or background process,driver, network stack, or any combination thereof, executing on a singlecomputer processor or multiple computer processors. Additionally,various steps of embodiments of the invention may provide one or moredata structures generated, produced, received, or otherwise implementedon a computer-readable medium, such as a memory.

Although embodiments of the present disclosure have been described indetail, those skilled in the art should understand that they may makevarious changes, substitutions and alterations herein without departingfrom the spirit and scope of the present disclosure. Accordingly, allsuch changes, substitutions and alterations are intended to be includedwithin the scope of the present disclosure as defined in the followingclaims.

1. A method of emulating a converged network, the method comprising: ata media gateway: receiving, at a first interface, a test call of a firstnetwork type; processing the test call for distribution on a secondnetwork type; transmitting the processed test call to a second interfaceof the second network type; and receiving, by way of a feedbackmechanism coupled with the second interface for conveying the test callfrom the media gateway back to the media gateway, the processed testcall, wherein the feedback mechanism includes ports of the first andsecond interfaces that are connected to each other, wherein the feedbackmechanism returns outbound traffic of the test call from the mediagateway to the media gateway, and wherein the returned test call trafficis treated as a separate call by the media gateway.
 2. The method ofclaim 1, wherein the feedback mechanism is coupled with the secondinterface and a third interface of the media gateway.
 3. The method ofclaim 1, wherein the feedback mechanism is coupled with a first port ofthe second interface and a second port of the second interface.
 4. Themethod of claim 1, wherein the first network type and the second networktype are respectively selected from the group consisting of a wirelessnetwork type, a public switched telephone network type, and an Internetprotocol network type.
 5. A method of emulating a converged network,comprising: receiving, by a media gateway controller, a call set-upmessage; obtaining a data element associated with the call set-upmessage; determining the data element is allocated for a test call;retrieving a configuration file associated with the data element thatspecifies one or more parameters of the test call; generating callcontrol messages according to the configuration file that instruct amedia gateway to use a feedback mechanism connecting a first networkinterface of the media gateway and having a first network type to asecond interface of the media gateway and having a second network type,wherein the feedback mechanism includes ports of the first and secondinterfaces that are connected to each other, wherein the feedbackmechanism returns outbound traffic of the test call from the mediagateway to the media gateway, and wherein the returned test call trafficis treated as a separate call by the media gateway; and transmitting thecall control messages to the media gateway.
 6. The method of claim 5,wherein obtaining the data element comprises obtaining a terminationidentifier.
 7. The method of claim 5, wherein retrieving a configurationfile further comprises retrieving a configuration file that specifiesone of more of a mapping between a physical and logical resource, atermination identifier identifying a termination point at the mediagateway for making a physical connection, and media bearer parameters.8. The method of claim 5, wherein the data element comprises aninterface type, a group number, and a member number of an originator ofthe call set-up message, and wherein determining the data element isallocated for a test call comprises determining the interface type, thegroup number, and the member number match a termination identifier of atrigger termination specified in the configuration file.
 9. A system foremulating a converged network, the system comprising: a media gatewaycontroller having a call generator and a network emulator respectivelyimplemented as computer-executable instructions, wherein the callgenerator generates a test call that is transmitted by the media gatewaycontroller; and a media gateway adapted to switch communications among aplurality of network types and communicatively coupled with the mediagateway controller, wherein the media gateway is configured with aplurality of network interfaces and has a feedback mechanism forconveying the test call from the media gateway back to the mediagateway, wherein the feedback mechanism includes ports of the first andsecond interfaces that are connected to each other, wherein the feedbackmechanism returns outbound traffic of the test call from the mediagateway to the media gateway, and wherein the returned test call trafficis treated as a separate call by the media gateway.
 10. The system ofclaim 9, wherein the feedback mechanism comprises a physical coupling.11. The system of claim 9, wherein the plurality of network interfacescomprises two or more interface cards selected from the group consistingof a wireless network interface card, a packet network interface card,and a wireline network interface card.
 12. The system of claim 9,wherein the network emulator includes a command monitor module thatmonitors for a test event and, in response to recognition of a testevent, invokes a test call procedure.
 13. The system of claim 12,wherein the test event comprises identifying a match between atermination identifier of the call and a termination identifierallocated for test calls.
 14. The system of claim 13, further comprisinga configuration file storage interfaced with the network emulator,wherein the network emulator reads a configuration file associated withthe termination identifier from the configuration file storage.
 15. Thesystem of claim 14, wherein the network emulator further comprises acommand parser and a control module, wherein the command parser isadapted to parse commands from the configuration file and transmit thecommands to the control module, and wherein the control module isadapted to generate call control messages in accordance with the parsedcommands and transmits the control messages to the media gateway.
 16. Acomputer-readable medium having computer-executable instructions forexecution by a processing system, the computer-executable instructionsfor facilitating converged network emulation, comprising: at a mediagateway: instructions that monitor for a test event; instructions that,responsive to detection of a test event, invoke a test call procedure;instructions that read a configuration file associated with the testevent; instructions that generate one or more call control messages fromthe configuration file, wherein the call control messages instruct amedia gateway to use a feedback mechanism connecting a first networkinterface of the media gateway and having a first network type to asecond interface of the media gateway and having a second network type,wherein the feedback mechanism includes ports of the first and secondinterfaces that are connected to each other, wherein the feedbackmechanism returns outbound traffic of the test call from the mediagateway to the media gateway, and wherein the returned test call trafficis treated as a separate call by the media gateway; and instructionsthat transmit the one or more call control messages to the mediagateway.
 17. The computer-readable medium of claim 16, wherein the testevent comprises identifying a match between a termination identifier ofa call and a termination identifier allocated for a test call.
 18. Thecomputer-readable medium of claim 17, wherein the configuration fileincludes a plurality of contexts each defining bearer characteristics ofa respective termination of the call.
 19. The computer-readable mediumof claim 18, wherein each of the plurality of contexts comprises bearercharacteristics selected from the group consisting of wireless bearercharacteristics, wireline bearer characteristics, and packet bearercharacteristics.
 20. The computer-readable medium of claim 16, whereinthe instructions that read the configuration file further compriseinstructions that read the configuration file from a configuration filestorage maintaining a plurality of configuration files each respectivelydefining a test call.
 21. The computer-readable medium of claim 16,further comprising instructions that generate a call and transmit thecall to the media gateway, wherein the call is processed according tothe control messages.
 22. A method for emulating a converged network,comprising: at a media gateway: assigning a first termination point withcharacteristics of a first network; assigning a second termination pointwith characteristics of a second network; configuring a connection, byway of a feedback mechanism for conveying a test call from the mediagateway back to the media gateway, between the first and secondtermination points, wherein the feedback mechanism includes ports of thefirst and second interfaces that are connected to each other; andtransmitting the test call from the first termination point to thesecond termination point using the feedback mechanism, wherein thefeedback mechanism returns outbound traffic of the test call from themedia gateway to the media gateway, and wherein the returned test calltraffic is treated as a separate call by the media gateway.
 23. Themethod of claim 22, wherein the characteristics of the first networkcomprise one or more wireline network bearer characteristics selectedfrom the group consisting of a codec, bandwidth, and echo cancellation,and wherein the characteristics of the second network comprise one ormore wireless network bearer characteristics selected from the groupconsisting of transcoder free operation, adaptive multi-rate speechcompression type, and echo cancellation.
 24. The method of claim 22,wherein the first termination point is configured with wireless networkbearer characteristics, and wherein transmitting the call from the firsttermination point to the second termination point emulates a wirelessnetwork handoff.